Skip to content

Revert "[Minor]: unify ANY/ALL planning and align ANY NULL semantics with PG (#21743)"#22345

Open
alamb wants to merge 1 commit into
apache:mainfrom
alamb:alamb/revert_any_pruning
Open

Revert "[Minor]: unify ANY/ALL planning and align ANY NULL semantics with PG (#21743)"#22345
alamb wants to merge 1 commit into
apache:mainfrom
alamb:alamb/revert_any_pruning

Conversation

@alamb
Copy link
Copy Markdown
Contributor

@alamb alamb commented May 18, 2026

Which issue does this PR close?

Rationale for this change

As @cetra3 describes on #22073, in #21743 @berkaysynnada made a seemingly small change to align to postgres semantics that had much larger consequences

I think many users (for example @cetra3) will treat this change as a regression, and thus I think this issue would block the next datafusion release

We tried an alternate fix but it appears to also raise some subtle questions from @Jefffrey

Thus I think it is safest to revert the initial change and work out the better longer term fix before releasing

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

sql SQL Planner sqllogictest SQL Logic Tests (.slt)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PR #21743 disables Parquet pruning for = ANY([literals])

1 participant